lazy evaluation for explode generator #52528
Open
+58
−12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Change
ExplodeBase.eval
to return anIterator
instead ofArray
.Why are the changes needed?
Returning an
Array
is requires that allInternalRow
objects be created in the call toExplodeBase.eval
. Using iteratorsMapExplodeIterator
andArrayExplodeIterator
the memory required for the explode operator is reduced.Does this PR introduce any user-facing change?
This PR has no user facing changes.
How was this patch tested?
Github Actions
Was this patch authored or co-authored using generative AI tooling?
The creation of this patch was assisted by Microsoft Copilot. The initial change was made using Agent mode.